Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd72b0c026aff882af30d37d68487fc73b7ef100da6f3152b0c8dcec13158fb3

Tx prefix hash: 71d029fdf239797ff1dadf54c323f733934daf7e0638bb18f35db9ac8d4c1592
Tx public key: a719c4eed986b72d88f9cd60f60666fd023bf63d2d0434818f3a5a1fe10d9bf8
Timestamp: 1712246999 Timestamp [UCT]: 2024-04-04 16:09:59 Age [y:d:h:m:s]: 01:040:06:52:23
Block: 993249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289811 RingCT/type: yes/0
Extra: 01a719c4eed986b72d88f9cd60f60666fd023bf63d2d0434818f3a5a1fe10d9bf802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27b078ef22366615cf0dfa9c11e7b90216f93437739fb13dd1ed7bd93bf4bda2 0.600000000000 1453635 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": 993259, "vin": [ { "gen": { "height": 993249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27b078ef22366615cf0dfa9c11e7b90216f93437739fb13dd1ed7bd93bf4bda2" } } ], "extra": [ 1, 167, 25, 196, 238, 217, 134, 183, 45, 136, 249, 205, 96, 246, 6, 102, 253, 2, 59, 246, 61, 45, 4, 52, 129, 143, 58, 90, 31, 225, 13, 155, 248, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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