Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 114ad42d973eac707c365d4ca4cd64d54f1ffff782362658c02b5f11764020d9

Tx prefix hash: 4ef5e0a9b43af69a3d6d9d9f7682bf82e65af37a7e16a3e53e1afba41f6ea0e0
Tx public key: 1c4ac24af594408786c24f452c240d57eae58faedb40432b13a91aab9df10494
Timestamp: 1577771282 Timestamp [UCT]: 2019-12-31 05:48:02 Age [y:d:h:m:s]: 04:362:15:24:48
Block: 35490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148346 RingCT/type: yes/0
Extra: 011c4ac24af594408786c24f452c240d57eae58faedb40432b13a91aab9df104940211000000088a2ee0d9000000000000000000

1 output(s) for total of 468.174496009000 dcy

stealth address amount amount idx
00: 664413a038689a5dd4a3644f855dcd48ba5a9b67ac76e2ea1e58429df64210c2 468.174496009000 59886 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": 35500, "vin": [ { "gen": { "height": 35490 } } ], "vout": [ { "amount": 468174496009, "target": { "key": "664413a038689a5dd4a3644f855dcd48ba5a9b67ac76e2ea1e58429df64210c2" } } ], "extra": [ 1, 28, 74, 194, 74, 245, 148, 64, 135, 134, 194, 79, 69, 44, 36, 13, 87, 234, 229, 143, 174, 219, 64, 67, 43, 19, 169, 26, 171, 157, 241, 4, 148, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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