Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a73d8a8f7ae0cb9b03989f4a62adf8c4f2856f9b707c9cee372817088104d6e2

Tx prefix hash: e67258ab622042d551616d9ec64348e0034bad13819e567f0943c67d36cab1c9
Tx public key: 272a688e3be7321a4afafa01bc37f92aa0f38da0265295e879675a131b34b7d4
Timestamp: 1714589671 Timestamp [UCT]: 2024-05-01 18:54:31 Age [y:d:h:m:s]: 01:190:20:13:29
Block: 1012706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395021 RingCT/type: yes/0
Extra: 01272a688e3be7321a4afafa01bc37f92aa0f38da0265295e879675a131b34b7d40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d6b8df28b9a89f6dbea24dd3b517ea6954f783771af2f8917680c997bdd081 0.600000000000 1475310 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": 1012716, "vin": [ { "gen": { "height": 1012706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d6b8df28b9a89f6dbea24dd3b517ea6954f783771af2f8917680c997bdd081" } } ], "extra": [ 1, 39, 42, 104, 142, 59, 231, 50, 26, 74, 250, 250, 1, 188, 55, 249, 42, 160, 243, 141, 160, 38, 82, 149, 232, 121, 103, 90, 19, 27, 52, 183, 212, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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