Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1d12bf2ae2a0ae36594cf816350ad0cee31700eb871c37b38947244569d9c92

Tx prefix hash: 141218c28ff94fb035eb3170baab764ce71a463cc6cffa840bbed294d98175e1
Tx public key: 7acb5f6f39d865c8831db3385bb6f7cb5823cb4ea2ed263c81f1de85e6ad8c91
Timestamp: 1705467214 Timestamp [UCT]: 2024-01-17 04:53:34 Age [y:d:h:m:s]: 01:322:08:41:05
Block: 937041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489274 RingCT/type: yes/0
Extra: 017acb5f6f39d865c8831db3385bb6f7cb5823cb4ea2ed263c81f1de85e6ad8c9102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f5e684dbefd79ae544dfa9cd06b6eb91a7a6e8650c20384dedc38ba0283812 0.600000000000 1395085 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": 937051, "vin": [ { "gen": { "height": 937041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f5e684dbefd79ae544dfa9cd06b6eb91a7a6e8650c20384dedc38ba0283812" } } ], "extra": [ 1, 122, 203, 95, 111, 57, 216, 101, 200, 131, 29, 179, 56, 91, 182, 247, 203, 88, 35, 203, 78, 162, 237, 38, 60, 129, 241, 222, 133, 230, 173, 140, 145, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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