Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e42de17f94ca3b4f2c46d8fca8712e89c51558d96daea513efcca5e355fa9ff

Tx prefix hash: 9af106d322670f373c8437c3e8a0906e9fd3c6b2cdd37a160fe20054db1f0fb1
Tx public key: 87008587a28cdfea855a028af1e3344023f297b7d0c88eb97a750a396f4d0483
Timestamp: 1676981516 Timestamp [UCT]: 2023-02-21 12:11:56 Age [y:d:h:m:s]: 02:048:22:18:43
Block: 701789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556566 RingCT/type: yes/0
Extra: 0187008587a28cdfea855a028af1e3344023f297b7d0c88eb97a750a396f4d048302110000000133af99f4000000000000000000

1 output(s) for total of 2.901894552000 dcy

stealth address amount amount idx
00: de303715ae32a420067c7e38214220bf568265a1d64df127e773ae686ae46c3d 2.901894552000 1145280 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": 701799, "vin": [ { "gen": { "height": 701789 } } ], "vout": [ { "amount": 2901894552, "target": { "key": "de303715ae32a420067c7e38214220bf568265a1d64df127e773ae686ae46c3d" } } ], "extra": [ 1, 135, 0, 133, 135, 162, 140, 223, 234, 133, 90, 2, 138, 241, 227, 52, 64, 35, 242, 151, 183, 208, 200, 142, 185, 122, 117, 10, 57, 111, 77, 4, 131, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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