Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6da060b8947d4baf47407bea952d5deb41e16a88b183ca55e39f07e31c0fd23

Tx prefix hash: e55aa2a06d62a45d6fdbe264ec30c2e9462587beb386b03bbcc45d7a58db5307
Tx public key: 019729a93b92ae789ef52b749d8de1ae99663f73234d02c3f317a117757bf4b4
Timestamp: 1720563574 Timestamp [UCT]: 2024-07-09 22:19:34 Age [y:d:h:m:s]: 01:120:22:23:49
Block: 1062231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344949 RingCT/type: yes/0
Extra: 01019729a93b92ae789ef52b749d8de1ae99663f73234d02c3f317a117757bf4b402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d59e961144933d4ea834d92c327a9bd680841e9d18963b4e58f19e5a5aafdecb 0.600000000000 1532732 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": 1062241, "vin": [ { "gen": { "height": 1062231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d59e961144933d4ea834d92c327a9bd680841e9d18963b4e58f19e5a5aafdecb" } } ], "extra": [ 1, 1, 151, 41, 169, 59, 146, 174, 120, 158, 245, 43, 116, 157, 141, 225, 174, 153, 102, 63, 115, 35, 77, 2, 195, 243, 23, 161, 23, 117, 123, 244, 180, 2, 17, 0, 0, 0, 4, 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