Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3734f3e69e470ebb72490b24bb2fb9d6c3eb99e9d872a63fc7b7ec51388b4aca

Tx prefix hash: b17a7d12a68a4a2fafd1055833cf51f6122faab9440f07d3f743d8e5eefbab06
Tx public key: a3e9f2c3a5afae573d8baecc44b2ee95014647ed078ead4f68d596876928b157
Timestamp: 1763457365 Timestamp [UCT]: 2025-11-18 09:16:05 Age [y:d:h:m:s]: 00:048:13:26:36
Block: 1414713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34791 RingCT/type: yes/0
Extra: 01a3e9f2c3a5afae573d8baecc44b2ee95014647ed078ead4f68d596876928b157021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78a40989116090705e916ff29cd7eaa5dc3eceaefcc9ce6d1c1cac6ecd626fa1 0.600000000000 1903204 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": 1414723, "vin": [ { "gen": { "height": 1414713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78a40989116090705e916ff29cd7eaa5dc3eceaefcc9ce6d1c1cac6ecd626fa1" } } ], "extra": [ 1, 163, 233, 242, 195, 165, 175, 174, 87, 61, 139, 174, 204, 68, 178, 238, 149, 1, 70, 71, 237, 7, 142, 173, 79, 104, 213, 150, 135, 105, 40, 177, 87, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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