Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec6fa49d4d1cb86a93040aa7cd8bbd292a0cf655c267f190dc034a50f97c28a1

Tx prefix hash: a701f54c69e0cfea4f46f3e9c85a3b0641452dbce915ad9bff05896d5e1107f2
Tx public key: 04dc62de64399a239aee17cb63a6a12004e542002ee3de1c15d07d717b703285
Timestamp: 1577060341 Timestamp [UCT]: 2019-12-23 00:19:01 Age [y:d:h:m:s]: 05:073:11:35:05
Block: 29782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202155 RingCT/type: yes/0
Extra: 0104dc62de64399a239aee17cb63a6a12004e542002ee3de1c15d07d717b70328502110000001b4ac5aa02000000000000000000

1 output(s) for total of 489.021800313000 dcy

stealth address amount amount idx
00: 735e44ffadd226006f8d12b77d9a01ac3d0c1bc3c4ba7d4e6a7d452ee2e337c2 489.021800313000 49080 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": 29792, "vin": [ { "gen": { "height": 29782 } } ], "vout": [ { "amount": 489021800313, "target": { "key": "735e44ffadd226006f8d12b77d9a01ac3d0c1bc3c4ba7d4e6a7d452ee2e337c2" } } ], "extra": [ 1, 4, 220, 98, 222, 100, 57, 154, 35, 154, 238, 23, 203, 99, 166, 161, 32, 4, 229, 66, 0, 46, 227, 222, 28, 21, 208, 125, 113, 123, 112, 50, 133, 2, 17, 0, 0, 0, 27, 74, 197, 170, 2, 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