Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497fa90aff8807b4f177a816d4518e109a7065fe281e41fb96ae4054fc744207

Tx prefix hash: e6cf476f24119b6252df42b93e57be277a54e8c2d1956daf4f19ca979f936175
Tx public key: 78f86b37b95a7fe07cb7edcfdbf21c7ac7bd9c571f99fd4bb524075348c3f491
Timestamp: 1706466900 Timestamp [UCT]: 2024-01-28 18:35:00 Age [y:d:h:m:s]: 00:349:18:18:26
Block: 945340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250408 RingCT/type: yes/0
Extra: 0178f86b37b95a7fe07cb7edcfdbf21c7ac7bd9c571f99fd4bb524075348c3f49102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d357e8569d61c34950fb4c1cbb1d7105ccb0c97ea51a3a00b3dffd60778bee 0.600000000000 1403652 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": 945350, "vin": [ { "gen": { "height": 945340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d357e8569d61c34950fb4c1cbb1d7105ccb0c97ea51a3a00b3dffd60778bee" } } ], "extra": [ 1, 120, 248, 107, 55, 185, 90, 127, 224, 124, 183, 237, 207, 219, 242, 28, 122, 199, 189, 156, 87, 31, 153, 253, 75, 181, 36, 7, 83, 72, 195, 244, 145, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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