Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ddf92900d1ca486593e1ce090a27dd458c01e8b556d81114f15535e7cff6a9

Tx prefix hash: b28912a0ca06c0e4b0cf692df6f2dc4ea745d77ec2c580ff766f416f6d1c7693
Tx public key: 92a9e863929826a9d4b47f9eff07465bf7170dd4475243d1c39a87a263b18722
Timestamp: 1721056210 Timestamp [UCT]: 2024-07-15 15:10:10 Age [y:d:h:m:s]: 00:263:08:17:13
Block: 1066325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188123 RingCT/type: yes/0
Extra: 0192a9e863929826a9d4b47f9eff07465bf7170dd4475243d1c39a87a263b1872202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1afd5ddb44ec75410d058851a4b05a0b0fbeebcb7ce97c92ec4464e689f2ae01 0.600000000000 1536898 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": 1066335, "vin": [ { "gen": { "height": 1066325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1afd5ddb44ec75410d058851a4b05a0b0fbeebcb7ce97c92ec4464e689f2ae01" } } ], "extra": [ 1, 146, 169, 232, 99, 146, 152, 38, 169, 212, 180, 127, 158, 255, 7, 70, 91, 247, 23, 13, 212, 71, 82, 67, 209, 195, 154, 135, 162, 99, 177, 135, 34, 2, 17, 0, 0, 0, 2, 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