Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0926ad784fb58caf01f564929ccc08648c3dcf4180098ca4bd8a389e27b7260c

Tx prefix hash: 0963d158001e827a3c61ebdd756b6279115fb1da8d2125fd167b123994fb8e68
Tx public key: 3d74dba19586ce3eee7f45105086c943b1d14039d0a18b552b6af8d938c44eba
Timestamp: 1587144593 Timestamp [UCT]: 2020-04-17 17:29:53 Age [y:d:h:m:s]: 05:045:03:46:43
Block: 93768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201402 RingCT/type: yes/0
Extra: 013d74dba19586ce3eee7f45105086c943b1d14039d0a18b552b6af8d938c44eba0211000001a96fa03929000000000000000000

1 output(s) for total of 300.129345440000 dcy

stealth address amount amount idx
00: 163440f66966cafd938b665d30a8ba2c6d3b3504da8beb7acf42a90b90d7e88c 300.129345440000 166866 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 93778, "vin": [ { "gen": { "height": 93768 } } ], "vout": [ { "amount": 300129345440, "target": { "key": "163440f66966cafd938b665d30a8ba2c6d3b3504da8beb7acf42a90b90d7e88c" } } ], "extra": [ 1, 61, 116, 219, 161, 149, 134, 206, 62, 238, 127, 69, 16, 80, 134, 201, 67, 177, 209, 64, 57, 208, 161, 139, 85, 43, 106, 248, 217, 56, 196, 78, 186, 2, 17, 0, 0, 1, 169, 111, 160, 57, 41, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8