Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41bd1e0a8123221e323dcc452addf142f6cca2e46ee08512b72918f38147f5f3

Tx prefix hash: 33d526d9bc50f2a0234fb9290560da1bf8f2167448904b8b717f31ca2864c0fb
Tx public key: 3e85790df11ba9f82c41855a2730115688899b2cf08a8cd8e7deecfb2a91df3e
Timestamp: 1707563298 Timestamp [UCT]: 2024-02-10 11:08:18 Age [y:d:h:m:s]: 01:057:13:34:13
Block: 954443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302172 RingCT/type: yes/0
Extra: 013e85790df11ba9f82c41855a2730115688899b2cf08a8cd8e7deecfb2a91df3e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf289bcb658a9706a59f3d14f4c51c12fed2e889c95a6f25a29aefa338eacc3d 0.600000000000 1413723 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": 954453, "vin": [ { "gen": { "height": 954443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf289bcb658a9706a59f3d14f4c51c12fed2e889c95a6f25a29aefa338eacc3d" } } ], "extra": [ 1, 62, 133, 121, 13, 241, 27, 169, 248, 44, 65, 133, 90, 39, 48, 17, 86, 136, 137, 155, 44, 240, 138, 140, 216, 231, 222, 236, 251, 42, 145, 223, 62, 2, 17, 0, 0, 0, 3, 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