Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 927712511578ff3c3727c83ef3ac95549cdba091d20c1e81db8650e889f30dad

Tx prefix hash: 265a8ff6f1b8a4b9eb4173ad6be885513ab65c25f64f2203c5f6743bfa5e0bc3
Tx public key: 8228e5c807b192d1b8ff0c7d56fa82c8204de7c12454f909ee6d1f98828ecdc0
Timestamp: 1717601872 Timestamp [UCT]: 2024-06-05 15:37:52 Age [y:d:h:m:s]: 00:348:04:21:37
Block: 1037671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248862 RingCT/type: yes/0
Extra: 018228e5c807b192d1b8ff0c7d56fa82c8204de7c12454f909ee6d1f98828ecdc00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4521495cee7d063c6abc259efc52f309a860773a93b5fb63480ada012614fa3 0.600000000000 1506224 of 15

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": 1037681, "vin": [ { "gen": { "height": 1037671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4521495cee7d063c6abc259efc52f309a860773a93b5fb63480ada012614fa3" } } ], "extra": [ 1, 130, 40, 229, 200, 7, 177, 146, 209, 184, 255, 12, 125, 86, 250, 130, 200, 32, 77, 231, 193, 36, 84, 249, 9, 238, 109, 31, 152, 130, 142, 205, 192, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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