Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb7c4bed12129e9eff6949e95140c4b0ac33ca914ae200c52110c5d6546c132

Tx prefix hash: c584ca60f1d301479dde217835f246e1c10d30f5943c0840d017158badc49151
Tx public key: 7249ae81efb473e74e782e5b42e2e8231c0487c44dc364248ecd9c2b26475d6a
Timestamp: 1727005212 Timestamp [UCT]: 2024-09-22 11:40:12 Age [y:d:h:m:s]: 00:107:09:01:03
Block: 1115633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76775 RingCT/type: yes/0
Extra: 017249ae81efb473e74e782e5b42e2e8231c0487c44dc364248ecd9c2b26475d6a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93ef1b5967b19f8213e2e35b3f44f77748dea1513ca2b5be8da429acf03acab1 0.600000000000 1595834 of 15

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": 1115643, "vin": [ { "gen": { "height": 1115633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93ef1b5967b19f8213e2e35b3f44f77748dea1513ca2b5be8da429acf03acab1" } } ], "extra": [ 1, 114, 73, 174, 129, 239, 180, 115, 231, 78, 120, 46, 91, 66, 226, 232, 35, 28, 4, 135, 196, 77, 195, 100, 36, 142, 205, 156, 43, 38, 71, 93, 106, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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