Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e317cd2829743373cb335350ee7d9a901040464bf32aaec7e0d87124dbb9bad

Tx prefix hash: 85a60c153afceb2db66425b9e6a298ff2bf96e77e6e0f6d6a2a302ae3471095a
Tx public key: 41ec2201cedc326aa1c34b74b38b20f46bdc7ff8a6c33713107b6871ca4278f3
Timestamp: 1702724843 Timestamp [UCT]: 2023-12-16 11:07:23 Age [y:d:h:m:s]: 01:130:02:09:02
Block: 914335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354121 RingCT/type: yes/0
Extra: 0141ec2201cedc326aa1c34b74b38b20f46bdc7ff8a6c33713107b6871ca4278f3021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5641279cdc6f37e7d3e3f9c22f0dbd1617fa54bae41930b2240c42aacdcde48c 0.600000000000 1371649 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": 914345, "vin": [ { "gen": { "height": 914335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5641279cdc6f37e7d3e3f9c22f0dbd1617fa54bae41930b2240c42aacdcde48c" } } ], "extra": [ 1, 65, 236, 34, 1, 206, 220, 50, 106, 161, 195, 75, 116, 179, 139, 32, 244, 107, 220, 127, 248, 166, 195, 55, 19, 16, 123, 104, 113, 202, 66, 120, 243, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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