Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168ca30ec1becfec49efbb7bbbbcd50b8cab1c5ba332bbed01f6259b1b107d7c

Tx prefix hash: 6558b3b60b01442d70929af86a62ee2727de389f9c7277992e988cbd85c7d19f
Tx public key: 419ae8c2f998ce8e7c67b38fd0dd48b040b93add8bedc945bb5294ea718fe27e
Timestamp: 1734527873 Timestamp [UCT]: 2024-12-18 13:17:53 Age [y:d:h:m:s]: 00:100:22:36:42
Block: 1177918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71901 RingCT/type: yes/0
Extra: 01419ae8c2f998ce8e7c67b38fd0dd48b040b93add8bedc945bb5294ea718fe27e02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd79e0662dcb5916f1f336bf6d63a2d22d1e9414aebb96b7f09ce49b11f6331 0.600000000000 1664299 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": 1177928, "vin": [ { "gen": { "height": 1177918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd79e0662dcb5916f1f336bf6d63a2d22d1e9414aebb96b7f09ce49b11f6331" } } ], "extra": [ 1, 65, 154, 232, 194, 249, 152, 206, 142, 124, 103, 179, 143, 208, 221, 72, 176, 64, 185, 58, 221, 139, 237, 201, 69, 187, 82, 148, 234, 113, 143, 226, 126, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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