Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc0876b1260772b9f7965a2d146119a0b25061539e4827a9066c5944e36b8c7

Tx prefix hash: d4600181df4ba4317fdf75242b43a9ab67100a07f8eb038d8b76006e47ba3b92
Tx public key: d658de885a7736db37b3cbd7eac74a55c82a5d19d3c9f58a74b3fd88012c85dc
Timestamp: 1724854173 Timestamp [UCT]: 2024-08-28 14:09:33 Age [y:d:h:m:s]: 01:072:22:05:33
Block: 1097790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310567 RingCT/type: yes/0
Extra: 01d658de885a7736db37b3cbd7eac74a55c82a5d19d3c9f58a74b3fd88012c85dc021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19f495689357a01eedb2189b23c72616f7b177609214beff7a33dea3d34e4953 0.600000000000 1573281 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": 1097800, "vin": [ { "gen": { "height": 1097790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19f495689357a01eedb2189b23c72616f7b177609214beff7a33dea3d34e4953" } } ], "extra": [ 1, 214, 88, 222, 136, 90, 119, 54, 219, 55, 179, 203, 215, 234, 199, 74, 85, 200, 42, 93, 25, 211, 201, 245, 138, 116, 179, 253, 136, 1, 44, 133, 220, 2, 17, 0, 0, 0, 2, 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