Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372485387492bf26423f1e3cb138141cadedfaddab767ecd1d816a5ba953df7b

Tx prefix hash: bb41c461e65bcc387f960d078480ba4abb6a927f0d1960d17ac47f31b12fc07c
Tx public key: cb157c6dbf37eb0a56b5b001c2fa218af2fa6ca38de5ab48b4bf49cff732e126
Timestamp: 1698012276 Timestamp [UCT]: 2023-10-22 22:04:36 Age [y:d:h:m:s]: 01:093:05:48:55
Block: 875467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327845 RingCT/type: yes/0
Extra: 01cb157c6dbf37eb0a56b5b001c2fa218af2fa6ca38de5ab48b4bf49cff732e12602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.771284182000 dcy

stealth address amount amount idx
00: 53cc57af547a0ecc1a6114d22fcdaeea0021c1cb201e297c48fa9c23e743f092 0.771284182000 1330723 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": 875477, "vin": [ { "gen": { "height": 875467 } } ], "vout": [ { "amount": 771284182, "target": { "key": "53cc57af547a0ecc1a6114d22fcdaeea0021c1cb201e297c48fa9c23e743f092" } } ], "extra": [ 1, 203, 21, 124, 109, 191, 55, 235, 10, 86, 181, 176, 1, 194, 250, 33, 138, 242, 250, 108, 163, 141, 229, 171, 72, 180, 191, 73, 207, 247, 50, 225, 38, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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