Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f0369039183b05cd4233354e0a1a67ebec7700a6616f4d63a68e14f22d273c

Tx prefix hash: 89e08ba08f8686a6c2c2b9e7ac61d9417e6aae3ffecc6b8a801cee39bc878690
Tx public key: dc140840375aea76c81f790fd60da3af86dec4ab30035dc6f7aa57ffa6fc53ab
Timestamp: 1649036672 Timestamp [UCT]: 2022-04-04 01:44:32 Age [y:d:h:m:s]: 02:278:10:00:06
Block: 472675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 718763 RingCT/type: yes/0
Extra: 01dc140840375aea76c81f790fd60da3af86dec4ab30035dc6f7aa57ffa6fc53ab021100000007a8c141c5000000000000000000

1 output(s) for total of 16.666014442000 dcy

stealth address amount amount idx
00: 00460b3af04068e8dce464413919d4e479451162a2a6854b4c803fbac322e9c7 16.666014442000 892338 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": 472685, "vin": [ { "gen": { "height": 472675 } } ], "vout": [ { "amount": 16666014442, "target": { "key": "00460b3af04068e8dce464413919d4e479451162a2a6854b4c803fbac322e9c7" } } ], "extra": [ 1, 220, 20, 8, 64, 55, 90, 234, 118, 200, 31, 121, 15, 214, 13, 163, 175, 134, 222, 196, 171, 48, 3, 93, 198, 247, 170, 87, 255, 166, 252, 83, 171, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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