Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46fcd70797a09cb6d3c3245cb7ce0c57d9337d3b3fb2548279578024ea23bd9

Tx prefix hash: 2d68cb5882bcc49071131884dfd443a474cc1ce090fe964b4604a584255090f5
Tx public key: e939cc0fb5baab3d064b184b49f48e68b74cfb61a67f66f9be756748b2236fff
Timestamp: 1728589750 Timestamp [UCT]: 2024-10-10 19:49:10 Age [y:d:h:m:s]: 00:189:10:11:34
Block: 1128770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135180 RingCT/type: yes/0
Extra: 01e939cc0fb5baab3d064b184b49f48e68b74cfb61a67f66f9be756748b2236fff02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d76ca881b33be68a66a6ce4551db54ed24e203c6ca84c8db80958f9384f924e 0.600000000000 1611591 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": 1128780, "vin": [ { "gen": { "height": 1128770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d76ca881b33be68a66a6ce4551db54ed24e203c6ca84c8db80958f9384f924e" } } ], "extra": [ 1, 233, 57, 204, 15, 181, 186, 171, 61, 6, 75, 24, 75, 73, 244, 142, 104, 183, 76, 251, 97, 166, 127, 102, 249, 190, 117, 103, 72, 178, 35, 111, 255, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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