Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c26de8aa484370e3a9ea3665d6796ba72ec0fe20e5f5fc021fea5d9734e2755

Tx prefix hash: 987799253ea7a1ead9202a8f6cc4bd8ec87b7813bcec2d71e594176242467c71
Tx public key: f7d45513bc761925ce0b85507ce58b9f568cf63593f8c720bfa094eef1680dff
Timestamp: 1764889756 Timestamp [UCT]: 2025-12-04 23:09:16 Age [y:d:h:m:s]: 00:056:12:56:31
Block: 1426595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40286 RingCT/type: yes/0
Extra: 01f7d45513bc761925ce0b85507ce58b9f568cf63593f8c720bfa094eef1680dff021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdac1fa52d0e7d815cf8dc28d1ea70eaf6a787612de0db99b91f815a4d11946 0.600000000000 1915288 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": 1426605, "vin": [ { "gen": { "height": 1426595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdac1fa52d0e7d815cf8dc28d1ea70eaf6a787612de0db99b91f815a4d11946" } } ], "extra": [ 1, 247, 212, 85, 19, 188, 118, 25, 37, 206, 11, 133, 80, 124, 229, 139, 159, 86, 140, 246, 53, 147, 248, 199, 32, 191, 160, 148, 238, 241, 104, 13, 255, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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