Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1486f80cd61af3cffcae8a301ce2bee056f4f01215d2543ce580fa958e04281

Tx prefix hash: acdd568413c04db90517650c73ac742e844a54326960a5afac20f45d382bcd13
Tx public key: 2571597a1d97aad2b0a630d1ad3db7de6cd8379fedfb7c25c4a7aacd934c699f
Timestamp: 1730634321 Timestamp [UCT]: 2024-11-03 11:45:21 Age [y:d:h:m:s]: 00:080:03:54:28
Block: 1145638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57308 RingCT/type: yes/0
Extra: 012571597a1d97aad2b0a630d1ad3db7de6cd8379fedfb7c25c4a7aacd934c699f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1be00fabd8af3356a46e61eef040e4b828bc5099aa7569ca0d916b772c92c66 0.600000000000 1630121 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": 1145648, "vin": [ { "gen": { "height": 1145638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1be00fabd8af3356a46e61eef040e4b828bc5099aa7569ca0d916b772c92c66" } } ], "extra": [ 1, 37, 113, 89, 122, 29, 151, 170, 210, 176, 166, 48, 209, 173, 61, 183, 222, 108, 216, 55, 159, 237, 251, 124, 37, 196, 167, 170, 205, 147, 76, 105, 159, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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