Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc88f1fe9401a40f858ed84313ffeb5de17ca4f7b34a2aa62790afdd7bdc62f4

Tx prefix hash: de72a109fd4c9738afb4cd622a729a4acfc7218dd055af9baab04fc31c7ed519
Tx public key: e0d79ae9d64138eb055312c380dd65df2133f3478baa3022668492e0db10c7c7
Timestamp: 1729777828 Timestamp [UCT]: 2024-10-24 13:50:28 Age [y:d:h:m:s]: 00:090:09:24:02
Block: 1138581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64587 RingCT/type: yes/0
Extra: 01e0d79ae9d64138eb055312c380dd65df2133f3478baa3022668492e0db10c7c70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df3fe3a2c5e4a1d9a7ef2d6cca976a68271fc2221aef7fdbc8411fd0ba0cdf28 0.600000000000 1622270 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": 1138591, "vin": [ { "gen": { "height": 1138581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df3fe3a2c5e4a1d9a7ef2d6cca976a68271fc2221aef7fdbc8411fd0ba0cdf28" } } ], "extra": [ 1, 224, 215, 154, 233, 214, 65, 56, 235, 5, 83, 18, 195, 128, 221, 101, 223, 33, 51, 243, 71, 139, 170, 48, 34, 102, 132, 146, 224, 219, 16, 199, 199, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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