Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb1cfde689bd20255e0332b247612619dc161554993b55605744edc189611e7d

Tx prefix hash: 737adb301e4c3385c299c4d843151fad9c72628a421fd51967294cebd49e94d5
Tx public key: 9a54cdc0882c059446a58df1d6d04b3524cda24c22019ab99cba0d0928beb972
Timestamp: 1712718593 Timestamp [UCT]: 2024-04-10 03:09:53 Age [y:d:h:m:s]: 01:000:21:07:14
Block: 997166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261599 RingCT/type: yes/0
Extra: 019a54cdc0882c059446a58df1d6d04b3524cda24c22019ab99cba0d0928beb972021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0abf9af196d6c89396d0f748ac3b18e3f0acd3cf1abd8c45ccb021822bdce85 0.600000000000 1457596 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": 997176, "vin": [ { "gen": { "height": 997166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0abf9af196d6c89396d0f748ac3b18e3f0acd3cf1abd8c45ccb021822bdce85" } } ], "extra": [ 1, 154, 84, 205, 192, 136, 44, 5, 148, 70, 165, 141, 241, 214, 208, 75, 53, 36, 205, 162, 76, 34, 1, 154, 185, 156, 186, 13, 9, 40, 190, 185, 114, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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