Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de07ce855f3f00c155ed81cd5c692cb77b4dffe518f0b6fb5980cbf6d9092383

Tx prefix hash: 3b90841725ea030a18a0f3991ad0405df4af1cd83f5858a8108575b6a62dc094
Tx public key: e5a0e932b6e45f7eeb9ce000d0e9eda2e9c779edc72ea82843fa3984a8e54957
Timestamp: 1666008157 Timestamp [UCT]: 2022-10-17 12:02:37 Age [y:d:h:m:s]: 02:198:06:25:58
Block: 610956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663375 RingCT/type: yes/0
Extra: 01e5a0e932b6e45f7eeb9ce000d0e9eda2e9c779edc72ea82843fa3984a8e54957021100000009faf35c9c000000000000000000

1 output(s) for total of 5.802954907000 dcy

stealth address amount amount idx
00: 1efc84d7d9e88bbf7422c05b80cde27acf3bfb4aa0f9d1f05420e8c3548d0d5f 5.802954907000 1047988 of 0

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": 610966, "vin": [ { "gen": { "height": 610956 } } ], "vout": [ { "amount": 5802954907, "target": { "key": "1efc84d7d9e88bbf7422c05b80cde27acf3bfb4aa0f9d1f05420e8c3548d0d5f" } } ], "extra": [ 1, 229, 160, 233, 50, 182, 228, 95, 126, 235, 156, 224, 0, 208, 233, 237, 162, 233, 199, 121, 237, 199, 46, 168, 40, 67, 250, 57, 132, 168, 229, 73, 87, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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