Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5e331ea40e7af1f7d81bd5a6489a588d6919a53edfbefc423daaa3f48e6e5f2

Tx prefix hash: 397910d9459ccb4ddc0fe0b67d07bc5d209c1931a717cd99f39f9ce29b9c848d
Tx public key: f70647b704382c341bfeb86921a756b7821fb83d3f925dc2902a8291e1c7ce50
Timestamp: 1709894738 Timestamp [UCT]: 2024-03-08 10:45:38 Age [y:d:h:m:s]: 01:011:00:15:36
Block: 973790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268871 RingCT/type: yes/0
Extra: 01f70647b704382c341bfeb86921a756b7821fb83d3f925dc2902a8291e1c7ce500211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d51f601425fd2a81871b025315e6fb45f79292e22a0c0e1a4d440049bff1441a 0.600000000000 1433729 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": 973800, "vin": [ { "gen": { "height": 973790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d51f601425fd2a81871b025315e6fb45f79292e22a0c0e1a4d440049bff1441a" } } ], "extra": [ 1, 247, 6, 71, 183, 4, 56, 44, 52, 27, 254, 184, 105, 33, 167, 86, 183, 130, 31, 184, 61, 63, 146, 93, 194, 144, 42, 130, 145, 225, 199, 206, 80, 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