Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b7fe4b27ac318bc415b2a6551642cd264ae6b0aed27e10a3d1dff4545813dde

Tx prefix hash: 28c69464d8a970d29e115a3485c3f214a1c8394f3c1f51631c51bcb46e0fe061
Tx public key: fd8968c8b12a2165dad61a53b08e8b339d555456cdc5bc03f6ee638c2ad1944c
Timestamp: 1723984927 Timestamp [UCT]: 2024-08-18 12:42:07 Age [y:d:h:m:s]: 01:106:14:26:19
Block: 1090594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334677 RingCT/type: yes/0
Extra: 01fd8968c8b12a2165dad61a53b08e8b339d555456cdc5bc03f6ee638c2ad1944c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6877a2a658f771f6b5d0aa06c819e2566cc6a945b65cbdaf5d4e0978edc134d4 0.600000000000 1565217 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": 1090604, "vin": [ { "gen": { "height": 1090594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6877a2a658f771f6b5d0aa06c819e2566cc6a945b65cbdaf5d4e0978edc134d4" } } ], "extra": [ 1, 253, 137, 104, 200, 177, 42, 33, 101, 218, 214, 26, 83, 176, 142, 139, 51, 157, 85, 84, 86, 205, 197, 188, 3, 246, 238, 99, 140, 42, 209, 148, 76, 2, 17, 0, 0, 0, 3, 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