Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b39c64f6712d134eee4927143cf740b7fd33c055f747ce9d04766af3d6d2f0ce

Tx prefix hash: 1dd7787a454bef218abee99366cb1b84bc59c0d79d82feea0a97d000f1e087b2
Tx public key: da990956e8bfb842498b81b5125401d70b54d82f7063d3e88a18a2ac0e144226
Timestamp: 1736605166 Timestamp [UCT]: 2025-01-11 14:19:26 Age [y:d:h:m:s]: 00:067:07:46:25
Block: 1195074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47921 RingCT/type: yes/0
Extra: 01da990956e8bfb842498b81b5125401d70b54d82f7063d3e88a18a2ac0e1442260211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07b03622d543e6d00c3b8e116462d2f32f1e0acb83184ae8e82084e90e5bf224 0.600000000000 1681659 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": 1195084, "vin": [ { "gen": { "height": 1195074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07b03622d543e6d00c3b8e116462d2f32f1e0acb83184ae8e82084e90e5bf224" } } ], "extra": [ 1, 218, 153, 9, 86, 232, 191, 184, 66, 73, 139, 129, 181, 18, 84, 1, 215, 11, 84, 216, 47, 112, 99, 211, 232, 138, 24, 162, 172, 14, 20, 66, 38, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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