Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eb3d09716e39062e4369fb3091028312c41a7b449f048c1872a221eec3441dc

Tx prefix hash: b08eb5eb303746f6843ca891ee76cb650a836c0e86d82d229dfa65adfae46a3b
Tx public key: fbfb2b5c7ae4ae80dc303923b187a9e628387d88e774b6f7a5e9c2338b30e8b5
Timestamp: 1625669609 Timestamp [UCT]: 2021-07-07 14:53:29 Age [y:d:h:m:s]: 03:331:13:29:46
Block: 289784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1007023 RingCT/type: yes/0
Extra: 01fbfb2b5c7ae4ae80dc303923b187a9e628387d88e774b6f7a5e9c2338b30e8b5021100000001ed79a617000000000000000000

1 output(s) for total of 67.273010103000 dcy

stealth address amount amount idx
00: 9096564cf49655f7c2254220254345856b3e05ff41f0859b7001345f2e49fef3 67.273010103000 607040 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": 289794, "vin": [ { "gen": { "height": 289784 } } ], "vout": [ { "amount": 67273010103, "target": { "key": "9096564cf49655f7c2254220254345856b3e05ff41f0859b7001345f2e49fef3" } } ], "extra": [ 1, 251, 251, 43, 92, 122, 228, 174, 128, 220, 48, 57, 35, 177, 135, 169, 230, 40, 56, 125, 136, 231, 116, 182, 247, 165, 233, 194, 51, 139, 48, 232, 181, 2, 17, 0, 0, 0, 1, 237, 121, 166, 23, 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