Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7bdbba39feace10c99005b4f6446341e5f8f2d96212cc20d98252f7987d5dd

Tx prefix hash: 276184a4b3bc963df316197c13e1666f8650814f8011e5261a8bb895f2857602
Tx public key: 15d8073503fe8d0d8b191fceb2c9139c70c715f8d6b84883938bf30999057f00
Timestamp: 1751411306 Timestamp [UCT]: 2025-07-01 23:08:26 Age [y:d:h:m:s]: 00:130:22:56:49
Block: 1316838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91819 RingCT/type: yes/0
Extra: 0115d8073503fe8d0d8b191fceb2c9139c70c715f8d6b84883938bf30999057f0002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 373f6ec1e5f8fe9cf642b85e60a81583603bcaf5d44d46c71f793ba1b5a472a3 0.600000000000 1804501 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": 1316848, "vin": [ { "gen": { "height": 1316838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "373f6ec1e5f8fe9cf642b85e60a81583603bcaf5d44d46c71f793ba1b5a472a3" } } ], "extra": [ 1, 21, 216, 7, 53, 3, 254, 141, 13, 139, 25, 31, 206, 178, 201, 19, 156, 112, 199, 21, 248, 214, 184, 72, 131, 147, 139, 243, 9, 153, 5, 127, 0, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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