Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a77c805c8bc6b043ecbf659c22ae6587041310215bf8c5e522597a3aef04e5

Tx prefix hash: cc58c258bb49e3d7a758b9cc34c07c29e43a06089f52c5331b57bae095aa11f0
Tx public key: 99b070e8de08cefab90317af1f94d421c2a74e80d119c751e47e3142eb7a15a8
Timestamp: 1760238606 Timestamp [UCT]: 2025-10-12 03:10:06 Age [y:d:h:m:s]: 00:088:15:46:39
Block: 1388031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63488 RingCT/type: yes/0
Extra: 0199b070e8de08cefab90317af1f94d421c2a74e80d119c751e47e3142eb7a15a8021100000005163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ae916454fe7af000e4ec624167b0e2cbbbb37d38ec5aff5108b849956ff52d 0.600000000000 1876226 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": 1388041, "vin": [ { "gen": { "height": 1388031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ae916454fe7af000e4ec624167b0e2cbbbb37d38ec5aff5108b849956ff52d" } } ], "extra": [ 1, 153, 176, 112, 232, 222, 8, 206, 250, 185, 3, 23, 175, 31, 148, 212, 33, 194, 167, 78, 128, 209, 25, 199, 81, 228, 126, 49, 66, 235, 122, 21, 168, 2, 17, 0, 0, 0, 5, 22, 49, 145, 238, 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