Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46407d796c90d1713c059b3dc69a8263d3263f315f6a69eb73b484559d25a8c6

Tx prefix hash: ce1d2c24bfdf41cc326f907e405a78136b60763277ac28da24fb9194ab0dc1ec
Tx public key: f984ed0a74aeaba6d47163cc44c8dcc63430a5437fc10e99a3f363a4652afc47
Timestamp: 1735833932 Timestamp [UCT]: 2025-01-02 16:05:32 Age [y:d:h:m:s]: 00:348:14:12:51
Block: 1188694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246686 RingCT/type: yes/0
Extra: 01f984ed0a74aeaba6d47163cc44c8dcc63430a5437fc10e99a3f363a4652afc470211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26ab7ea56ad6140f1faa01a83b246e90b585a6a37483fbbb42982a9b910a2b84 0.600000000000 1675197 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": 1188704, "vin": [ { "gen": { "height": 1188694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ab7ea56ad6140f1faa01a83b246e90b585a6a37483fbbb42982a9b910a2b84" } } ], "extra": [ 1, 249, 132, 237, 10, 116, 174, 171, 166, 212, 113, 99, 204, 68, 200, 220, 198, 52, 48, 165, 67, 127, 193, 14, 153, 163, 243, 99, 164, 101, 42, 252, 71, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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