Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724f34f15a6d7f2f4acb0da4d56824512c1bb07fc5bb1f4f0587947383bac917

Tx prefix hash: 46b96edd4624918091d8917665f98cd31105d77e03a4ea11f1c2aefa831f48b1
Tx public key: 50c32308a1be8435abf10587a4dcace047770a9f911b02ea98849672b9955a90
Timestamp: 1711186920 Timestamp [UCT]: 2024-03-23 09:42:00 Age [y:d:h:m:s]: 01:231:06:27:41
Block: 984509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423967 RingCT/type: yes/0
Extra: 0150c32308a1be8435abf10587a4dcace047770a9f911b02ea98849672b9955a900211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e5c504294c5fd5a9c31ae080b597bf19db1d3bbf4fa06de0a62fa3a80606517 0.600000000000 1444680 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": 984519, "vin": [ { "gen": { "height": 984509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e5c504294c5fd5a9c31ae080b597bf19db1d3bbf4fa06de0a62fa3a80606517" } } ], "extra": [ 1, 80, 195, 35, 8, 161, 190, 132, 53, 171, 241, 5, 135, 164, 220, 172, 224, 71, 119, 10, 159, 145, 27, 2, 234, 152, 132, 150, 114, 185, 149, 90, 144, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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