Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ad1fcaf145f18c5d46db7d4e64a6ffadce0239a45d46c1aabf70045fb0db5d

Tx prefix hash: 0957bb3d5be16c63363dbb77a2b91a28fbfe3b1c874e80c4622cb722c60bea7a
Tx public key: d662ae768bfc4ea33f8cad9aa4f952e636ebb0735c9ac793453126d9da78578f
Timestamp: 1631566613 Timestamp [UCT]: 2021-09-13 20:56:53 Age [y:d:h:m:s]: 03:055:21:55:08
Block: 333169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 815548 RingCT/type: yes/0
Extra: 01d662ae768bfc4ea33f8cad9aa4f952e636ebb0735c9ac793453126d9da78578f02110000000e37cb3088000000000000000000

1 output(s) for total of 48.314027244000 dcy

stealth address amount amount idx
00: 1455e72cc8e4ee80757edd2465bad18d76864e702c66540efd59f7cbf28e178e 48.314027244000 687644 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": 333179, "vin": [ { "gen": { "height": 333169 } } ], "vout": [ { "amount": 48314027244, "target": { "key": "1455e72cc8e4ee80757edd2465bad18d76864e702c66540efd59f7cbf28e178e" } } ], "extra": [ 1, 214, 98, 174, 118, 139, 252, 78, 163, 63, 140, 173, 154, 164, 249, 82, 230, 54, 235, 176, 115, 92, 154, 199, 147, 69, 49, 38, 217, 218, 120, 87, 143, 2, 17, 0, 0, 0, 14, 55, 203, 48, 136, 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