Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656546bd8d5b5b2d7159c43a2a227a2b4217b86e8a14a169bf40d2379ef3e58f

Tx prefix hash: d8a8c910f3ff80a9d3a74df3236e87f35f8d6d4ed5affd0243b98ba98f2d3c30
Tx public key: 03617022433f37ea3b08c8561f3dbfdfd4839e880cd96d412639663027e50fef
Timestamp: 1701974192 Timestamp [UCT]: 2023-12-07 18:36:32 Age [y:d:h:m:s]: 01:151:17:18:39
Block: 908117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369592 RingCT/type: yes/0
Extra: 0103617022433f37ea3b08c8561f3dbfdfd4839e880cd96d412639663027e50fef0211000000024b8f5122000000000000000000

1 output(s) for total of 0.601217168000 dcy

stealth address amount amount idx
00: b64cbc02eda1ecc07d1aed50368ef3a1db144c4cbd58e40593859fa0924d1711 0.601217168000 1365140 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": 908127, "vin": [ { "gen": { "height": 908117 } } ], "vout": [ { "amount": 601217168, "target": { "key": "b64cbc02eda1ecc07d1aed50368ef3a1db144c4cbd58e40593859fa0924d1711" } } ], "extra": [ 1, 3, 97, 112, 34, 67, 63, 55, 234, 59, 8, 200, 86, 31, 61, 191, 223, 212, 131, 158, 136, 12, 217, 109, 65, 38, 57, 102, 48, 39, 229, 15, 239, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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