Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49ae806850f011a6fb7eb4e1721bd751ac5b1ad0aabe7d7c2dd2dc4b2d404513

Tx prefix hash: 4edd720da8f25436c94a6bd9841d21cdfdffbc6451fe3b98bcce3234ad6a4612
Tx public key: e77fd9a4aaf9d46ca40a4de531cbb328873f715d45c0d4103263b165a878e4c2
Timestamp: 1720574975 Timestamp [UCT]: 2024-07-10 01:29:35 Age [y:d:h:m:s]: 00:212:09:38:23
Block: 1062329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151712 RingCT/type: yes/0
Extra: 01e77fd9a4aaf9d46ca40a4de531cbb328873f715d45c0d4103263b165a878e4c2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85803818baef27256467ba53aa91b7eb799ab3abdbc98a14276ce126c7e999dd 0.600000000000 1532830 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": 1062339, "vin": [ { "gen": { "height": 1062329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85803818baef27256467ba53aa91b7eb799ab3abdbc98a14276ce126c7e999dd" } } ], "extra": [ 1, 231, 127, 217, 164, 170, 249, 212, 108, 164, 10, 77, 229, 49, 203, 179, 40, 135, 63, 113, 93, 69, 192, 212, 16, 50, 99, 177, 101, 168, 120, 228, 194, 2, 17, 0, 0, 0, 3, 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