Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363cea463fd2c0bf30b277c678deae60ef6407c1be9465d2d1f699985674714f

Tx prefix hash: 1733f89d2b48b6fdcf54b0ad7588fb5dd9e841992c5f8d257ab3c236eca51854
Tx public key: 16a9979d10fcc82e61a9f0b809aa13e8694a7dfa110eb34c79ee2b8ada7c6aa7
Timestamp: 1617092741 Timestamp [UCT]: 2021-03-30 08:25:41 Age [y:d:h:m:s]: 04:219:15:10:00
Block: 229579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174815 RingCT/type: yes/0
Extra: 0116a9979d10fcc82e61a9f0b809aa13e8694a7dfa110eb34c79ee2b8ada7c6aa702110000001c9c1fbdcc000000000000000000

1 output(s) for total of 106.490300473000 dcy

stealth address amount amount idx
00: 902ea5f8b0ba487812ab01f12676d478fe0f79f685f3acc2f058bd6761e5d028 106.490300473000 476399 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": 229589, "vin": [ { "gen": { "height": 229579 } } ], "vout": [ { "amount": 106490300473, "target": { "key": "902ea5f8b0ba487812ab01f12676d478fe0f79f685f3acc2f058bd6761e5d028" } } ], "extra": [ 1, 22, 169, 151, 157, 16, 252, 200, 46, 97, 169, 240, 184, 9, 170, 19, 232, 105, 74, 125, 250, 17, 14, 179, 76, 121, 238, 43, 138, 218, 124, 106, 167, 2, 17, 0, 0, 0, 28, 156, 31, 189, 204, 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