Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64445d2a1a382b0133ba286a46e3572a77c3253b7956651aa8844928fe195921

Tx prefix hash: 85d60a9a48f51c83dbd0aaf6d05375fbfadc177c3f5feef7994f2312b62a1d41
Tx public key: 92a7542e9e6894dfe1b26806ed9cf57b1b691a0108635069787c3d94b07adfd2
Timestamp: 1724940770 Timestamp [UCT]: 2024-08-29 14:12:50 Age [y:d:h:m:s]: 01:062:15:28:11
Block: 1098519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303212 RingCT/type: yes/0
Extra: 0192a7542e9e6894dfe1b26806ed9cf57b1b691a0108635069787c3d94b07adfd202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c3951c4ebd1f44c4ef77f32cb39ba24f290b9995758854bf916f3b03d46d8f6 0.600000000000 1574260 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": 1098529, "vin": [ { "gen": { "height": 1098519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c3951c4ebd1f44c4ef77f32cb39ba24f290b9995758854bf916f3b03d46d8f6" } } ], "extra": [ 1, 146, 167, 84, 46, 158, 104, 148, 223, 225, 178, 104, 6, 237, 156, 245, 123, 27, 105, 26, 1, 8, 99, 80, 105, 120, 124, 61, 148, 176, 122, 223, 210, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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