Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c03e4ffb875be5fb6b72d7db57d350ddbae7c73b192662b2af956af696ede68

Tx prefix hash: b26219ff069ad168c04c18d2b80f0db3fcd176286a595ab5814b4a170ba02fbc
Tx public key: cdb87695b6407d7e3064f82d8e926c1b64a821b947410e98358915531f7b1eb5
Timestamp: 1731161355 Timestamp [UCT]: 2024-11-09 14:09:15 Age [y:d:h:m:s]: 00:130:08:02:22
Block: 1150009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92986 RingCT/type: yes/0
Extra: 01cdb87695b6407d7e3064f82d8e926c1b64a821b947410e98358915531f7b1eb5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57b642c1f099db660dce85c7a243e8053390cd6975b72f656dac88d1eb4fa087 0.600000000000 1635202 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": 1150019, "vin": [ { "gen": { "height": 1150009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57b642c1f099db660dce85c7a243e8053390cd6975b72f656dac88d1eb4fa087" } } ], "extra": [ 1, 205, 184, 118, 149, 182, 64, 125, 126, 48, 100, 248, 45, 142, 146, 108, 27, 100, 168, 33, 185, 71, 65, 14, 152, 53, 137, 21, 83, 31, 123, 30, 181, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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