Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7316982a1fd633eb575a8d7635f8360e2fcc50dda4fb3c9d1f1840423d5fc263

Tx prefix hash: 2b6d809e969cd62de32388a3c66fbedf29ec9376c13b9ba140dff8409eaa9351
Tx public key: 10d10fd4f80f5630af84d3d335afca0d7de9f49c3928f298b405001037bd8848
Timestamp: 1634285328 Timestamp [UCT]: 2021-10-15 08:08:48 Age [y:d:h:m:s]: 03:072:10:06:50
Block: 353437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829608 RingCT/type: yes/0
Extra: 0110d10fd4f80f5630af84d3d335afca0d7de9f49c3928f298b405001037bd88480211000000153fc41461000000000000000000

1 output(s) for total of 41.392048370000 dcy

stealth address amount amount idx
00: 63791ccd5975cd25c39d597b741dd4e85a39116cf6cb0dc32cb65897f942afd9 41.392048370000 722231 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": 353447, "vin": [ { "gen": { "height": 353437 } } ], "vout": [ { "amount": 41392048370, "target": { "key": "63791ccd5975cd25c39d597b741dd4e85a39116cf6cb0dc32cb65897f942afd9" } } ], "extra": [ 1, 16, 209, 15, 212, 248, 15, 86, 48, 175, 132, 211, 211, 53, 175, 202, 13, 125, 233, 244, 156, 57, 40, 242, 152, 180, 5, 0, 16, 55, 189, 136, 72, 2, 17, 0, 0, 0, 21, 63, 196, 20, 97, 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