Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f9d38106e89c281938c25e0d3de4c0295980ad41548c15cb1f3e2a205c4ea33

Tx prefix hash: 5931d148ed0bf1c365d20bf065aa573768e85b1cb0691e6757b747f3c66f07e3
Tx public key: ead651b1714aafb8a4234c9b89ab0c7260aff801b65e49e5bb51ba07ca418d78
Timestamp: 1727263467 Timestamp [UCT]: 2024-09-25 11:24:27 Age [y:d:h:m:s]: 00:150:23:30:24
Block: 1117778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107669 RingCT/type: yes/0
Extra: 01ead651b1714aafb8a4234c9b89ab0c7260aff801b65e49e5bb51ba07ca418d7802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f69fe2558f5885852358ec1429db81041bfd12e2e9134e9b8d0a82d1cf8e4d7 0.600000000000 1598737 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": 1117788, "vin": [ { "gen": { "height": 1117778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f69fe2558f5885852358ec1429db81041bfd12e2e9134e9b8d0a82d1cf8e4d7" } } ], "extra": [ 1, 234, 214, 81, 177, 113, 74, 175, 184, 164, 35, 76, 155, 137, 171, 12, 114, 96, 175, 248, 1, 182, 94, 73, 229, 187, 81, 186, 7, 202, 65, 141, 120, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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