Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866a118fd17cd158b963ce4f500c950a237858c8387709a8c9cfdf82efb40bd7

Tx prefix hash: ebc02a8e84037c07a96c3ac86f071f31a551423ce34c47b371bc9e8f0781b170
Tx public key: 220d90610820ce9db5a67a3c518a12d8bcd7ec9cbca8a68a8556945fc4d3cfd7
Timestamp: 1676969056 Timestamp [UCT]: 2023-02-21 08:44:16 Age [y:d:h:m:s]: 02:004:02:11:33
Block: 701686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524487 RingCT/type: yes/0
Extra: 01220d90610820ce9db5a67a3c518a12d8bcd7ec9cbca8a68a8556945fc4d3cfd7021100000002faf35c9c000000000000000000

1 output(s) for total of 2.904175846000 dcy

stealth address amount amount idx
00: 5fc66532b5f3d3260f80f553def780bbe70f31add88de64cec35d20802682859 2.904175846000 1145173 of 0

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": 701696, "vin": [ { "gen": { "height": 701686 } } ], "vout": [ { "amount": 2904175846, "target": { "key": "5fc66532b5f3d3260f80f553def780bbe70f31add88de64cec35d20802682859" } } ], "extra": [ 1, 34, 13, 144, 97, 8, 32, 206, 157, 181, 166, 122, 60, 81, 138, 18, 216, 188, 215, 236, 156, 188, 168, 166, 138, 133, 86, 148, 95, 196, 211, 207, 215, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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