Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5625958188c4dac468817e48a8b0580b30cad28b563e1f947dbf98f4d67510d0

Tx prefix hash: 6a1215952c3fc4a5153ff9ab8673dce16480d91d58ea3e0e8f7edd8048932106
Tx public key: f4efa3ec2f29bd4ad286afd0d43c704b7529c3f5cd6d82ce996fdbf80b56f1ba
Timestamp: 1703859367 Timestamp [UCT]: 2023-12-29 14:16:07 Age [y:d:h:m:s]: 01:102:20:33:27
Block: 923743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334625 RingCT/type: yes/0
Extra: 01f4efa3ec2f29bd4ad286afd0d43c704b7529c3f5cd6d82ce996fdbf80b56f1ba021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be001dc272cccf7eef404530e205d205090299624938f63ed0ed11cf48343d6 0.600000000000 1381479 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": 923753, "vin": [ { "gen": { "height": 923743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be001dc272cccf7eef404530e205d205090299624938f63ed0ed11cf48343d6" } } ], "extra": [ 1, 244, 239, 163, 236, 47, 41, 189, 74, 210, 134, 175, 208, 212, 60, 112, 75, 117, 41, 195, 245, 205, 109, 130, 206, 153, 111, 219, 248, 11, 86, 241, 186, 2, 17, 0, 0, 0, 2, 173, 86, 148, 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