Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c7a8544b9ac716d4fe446ba06d199b00ab2b3abc417a5d3212312d520f7b5ab

Tx prefix hash: c94a567de6d313f0c0ddc47a0f15c58f4972a8b3a2c6a07b1745ae5e990ec841
Tx public key: d0ae1030ef744a4e47bb49b263754403cf17ace683ef9fe1f0f92507f3fba4af
Timestamp: 1713343010 Timestamp [UCT]: 2024-04-17 08:36:50 Age [y:d:h:m:s]: 00:351:11:44:39
Block: 1002361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251275 RingCT/type: yes/0
Extra: 01d0ae1030ef744a4e47bb49b263754403cf17ace683ef9fe1f0f92507f3fba4af02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35183eed9e4a2aa9b880e7c267f158af2624b32486218d1660283a717430fbd2 0.600000000000 1462877 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": 1002371, "vin": [ { "gen": { "height": 1002361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35183eed9e4a2aa9b880e7c267f158af2624b32486218d1660283a717430fbd2" } } ], "extra": [ 1, 208, 174, 16, 48, 239, 116, 74, 78, 71, 187, 73, 178, 99, 117, 68, 3, 207, 23, 172, 230, 131, 239, 159, 225, 240, 249, 37, 7, 243, 251, 164, 175, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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