Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e0c3b72c3275e52598727d2f1aff472c346d692d1e05f6479f2dfb7842db62e

Tx prefix hash: 0942622b23dfa09ae829a7bd9f4a1fc3712ba7682c0607689032e3ad7636305d
Tx public key: c8322f4b834d30382e840eab51e0899f9bfc1dc80d1b8b1eae50c400cd60bd59
Timestamp: 1720397501 Timestamp [UCT]: 2024-07-08 00:11:41 Age [y:d:h:m:s]: 00:230:03:42:17
Block: 1060845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164395 RingCT/type: yes/0
Extra: 01c8322f4b834d30382e840eab51e0899f9bfc1dc80d1b8b1eae50c400cd60bd59021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2b40384767cbce60f9094d3f6d0fd5590f6f4368f3f286ad2b045bb7e4a87c3 0.600000000000 1531332 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": 1060855, "vin": [ { "gen": { "height": 1060845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2b40384767cbce60f9094d3f6d0fd5590f6f4368f3f286ad2b045bb7e4a87c3" } } ], "extra": [ 1, 200, 50, 47, 75, 131, 77, 48, 56, 46, 132, 14, 171, 81, 224, 137, 159, 155, 252, 29, 200, 13, 27, 139, 30, 174, 80, 196, 0, 205, 96, 189, 89, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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