Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ad86b551269443ce30255d78b612e94a41e76378437922a9f47dd3c3b99b41

Tx prefix hash: c0a04ef8430538497ddb43f173f427e7b4370671fe4532c08ffb056252558922
Tx public key: 092f46fba4b1f1e8bd0f50422cd37ee350102958b3850de1b1e39fc0cb2cf522
Timestamp: 1723440371 Timestamp [UCT]: 2024-08-12 05:26:11 Age [y:d:h:m:s]: 00:292:04:37:29
Block: 1086076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208763 RingCT/type: yes/0
Extra: 01092f46fba4b1f1e8bd0f50422cd37ee350102958b3850de1b1e39fc0cb2cf52202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c9b56d2c27653cbf26297a9dc3079b401a0b5ee8b44ab686f77470eb5cd0d9 0.600000000000 1560669 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": 1086086, "vin": [ { "gen": { "height": 1086076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c9b56d2c27653cbf26297a9dc3079b401a0b5ee8b44ab686f77470eb5cd0d9" } } ], "extra": [ 1, 9, 47, 70, 251, 164, 177, 241, 232, 189, 15, 80, 66, 44, 211, 126, 227, 80, 16, 41, 88, 179, 133, 13, 225, 177, 227, 159, 192, 203, 44, 245, 34, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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