Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ca5325b27113dd4d0400ab81f3990d58df168f21f791063996a4229e999e6b

Tx prefix hash: 4cdaa1807c897947877d44efc416fe280d4e19486b08d4acfe8f5cc81c5ad340
Tx public key: 96f6d61c1f63faf88ac9f2cb4d25684ca3f20d69c87c05740d87ec030f9b0854
Timestamp: 1749593823 Timestamp [UCT]: 2025-06-10 22:17:03 Age [y:d:h:m:s]: 00:161:13:13:58
Block: 1302348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113140 RingCT/type: yes/0
Extra: 0196f6d61c1f63faf88ac9f2cb4d25684ca3f20d69c87c05740d87ec030f9b0854021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69089dfe9da3f89bda5f06343982c5fe6ffb62ea2dd719dba7bd4c7af25fd8c4 0.600000000000 1789917 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": 1302358, "vin": [ { "gen": { "height": 1302348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69089dfe9da3f89bda5f06343982c5fe6ffb62ea2dd719dba7bd4c7af25fd8c4" } } ], "extra": [ 1, 150, 246, 214, 28, 31, 99, 250, 248, 138, 201, 242, 203, 77, 37, 104, 76, 163, 242, 13, 105, 200, 124, 5, 116, 13, 135, 236, 3, 15, 155, 8, 84, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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