Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9586941e43bc8680be20b93fd2909ecde53d137c9a8ce411298951df992c41

Tx prefix hash: 602f7e4a6690c79fef5412aa9259a86acdddf49a00bf2b5350b472a5954476d8
Tx public key: 1ac15f0f6f5d2dffbfae8b73d2cce984043144b9c8e47e39086c07662362a0c9
Timestamp: 1711156016 Timestamp [UCT]: 2024-03-23 01:06:56 Age [y:d:h:m:s]: 01:067:08:24:14
Block: 984257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309142 RingCT/type: yes/0
Extra: 011ac15f0f6f5d2dffbfae8b73d2cce984043144b9c8e47e39086c07662362a0c90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34343c4e0ceacb16993b670e545750fa320ff6cdba2ba12359e5d2d257b0d49 0.600000000000 1444426 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": 984267, "vin": [ { "gen": { "height": 984257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34343c4e0ceacb16993b670e545750fa320ff6cdba2ba12359e5d2d257b0d49" } } ], "extra": [ 1, 26, 193, 95, 15, 111, 93, 45, 255, 191, 174, 139, 115, 210, 204, 233, 132, 4, 49, 68, 185, 200, 228, 126, 57, 8, 108, 7, 102, 35, 98, 160, 201, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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