Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745de316ed60e82ea37f2ddbf6e1c9c57d74d6b9285e31956d75c38dbcdec600

Tx prefix hash: 4fdc5597130268e708477eb5f2dd5098e51688140cd50bbedfec40ff5f239283
Tx public key: b66e4636f7d15fe98d439a16ff8ca2fa92df9e69810f5028b1d4e608e9f039cd
Timestamp: 1677916653 Timestamp [UCT]: 2023-03-04 07:57:33 Age [y:d:h:m:s]: 01:358:17:35:04
Block: 709550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517050 RingCT/type: yes/0
Extra: 01b66e4636f7d15fe98d439a16ff8ca2fa92df9e69810f5028b1d4e608e9f039cd0211000000055029cbac000000000000000000

1 output(s) for total of 2.735055863000 dcy

stealth address amount amount idx
00: 3f2a33b6ae70af284099448eb9bb3e6a240ae1fedaf8aa9d14d4caf814861e07 2.735055863000 1153541 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": 709560, "vin": [ { "gen": { "height": 709550 } } ], "vout": [ { "amount": 2735055863, "target": { "key": "3f2a33b6ae70af284099448eb9bb3e6a240ae1fedaf8aa9d14d4caf814861e07" } } ], "extra": [ 1, 182, 110, 70, 54, 247, 209, 95, 233, 141, 67, 154, 22, 255, 140, 162, 250, 146, 223, 158, 105, 129, 15, 80, 40, 177, 212, 230, 8, 233, 240, 57, 205, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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