Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca8b398d5f200351bdd1c457af8fda5bea13c20338ddb6235154c212e0da1a6

Tx prefix hash: b59632fa0f6ec01f911c29c9cd46c5581f497b624373964089ec62de5f3f5d1a
Tx public key: 10896a1bf0f795f84c93a21ad062d1d31bb8d4fd3778246cade6c08f860bcbaf
Timestamp: 1711094747 Timestamp [UCT]: 2024-03-22 08:05:47 Age [y:d:h:m:s]: 01:028:00:39:15
Block: 983751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280993 RingCT/type: yes/0
Extra: 0110896a1bf0f795f84c93a21ad062d1d31bb8d4fd3778246cade6c08f860bcbaf0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f791e3ec05128c6bd68c1e6459e6f518c872e27fdff69bbaa94d2f20df6d5a5b 0.600000000000 1443894 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": 983761, "vin": [ { "gen": { "height": 983751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f791e3ec05128c6bd68c1e6459e6f518c872e27fdff69bbaa94d2f20df6d5a5b" } } ], "extra": [ 1, 16, 137, 106, 27, 240, 247, 149, 248, 76, 147, 162, 26, 208, 98, 209, 211, 27, 184, 212, 253, 55, 120, 36, 108, 173, 230, 192, 143, 134, 11, 203, 175, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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