Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db156c1ae5bc80ec8618d718a5710002f012f7776477fde2744a8453724d4b1f

Tx prefix hash: 3b3ce9c74a96f77ca95db0435638d9149c75ce627817e105a154e5b977e76fd8
Tx public key: 5735676efe797e5b6e802e8b66da1dcf356c9e66962fa1cced0588416ac5dc8f
Timestamp: 1721608218 Timestamp [UCT]: 2024-07-22 00:30:18 Age [y:d:h:m:s]: 00:217:12:10:23
Block: 1070874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155343 RingCT/type: yes/0
Extra: 015735676efe797e5b6e802e8b66da1dcf356c9e66962fa1cced0588416ac5dc8f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8081dca81149426fbe7b4ab4633f6e96e016f0810587425c4f0e8279e9c8d7d5 0.600000000000 1542889 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": 1070884, "vin": [ { "gen": { "height": 1070874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8081dca81149426fbe7b4ab4633f6e96e016f0810587425c4f0e8279e9c8d7d5" } } ], "extra": [ 1, 87, 53, 103, 110, 254, 121, 126, 91, 110, 128, 46, 139, 102, 218, 29, 207, 53, 108, 158, 102, 150, 47, 161, 204, 237, 5, 136, 65, 106, 197, 220, 143, 2, 17, 0, 0, 0, 7, 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