Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c699676315a01f9ae4fe40fe93ee2ee866c1524d19d4858661ab2726cf324fe1

Tx prefix hash: be4d04511695c0c318eaa568b891d9ee9eccc0b57acd8097de2c9790817f878b
Tx public key: eaf4ecc2493a59bf0765597fc8522506d596b1fb1ea9ae560806dd917a443c7d
Timestamp: 1715204371 Timestamp [UCT]: 2024-05-08 21:39:31 Age [y:d:h:m:s]: 01:183:23:50:14
Block: 1017811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390104 RingCT/type: yes/0
Extra: 01eaf4ecc2493a59bf0765597fc8522506d596b1fb1ea9ae560806dd917a443c7d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8913e457fb1da6e00a75dc2cc78d207f1220eab5f2a4e412068dfd56024b785 0.600000000000 1481596 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": 1017821, "vin": [ { "gen": { "height": 1017811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8913e457fb1da6e00a75dc2cc78d207f1220eab5f2a4e412068dfd56024b785" } } ], "extra": [ 1, 234, 244, 236, 194, 73, 58, 89, 191, 7, 101, 89, 127, 200, 82, 37, 6, 213, 150, 177, 251, 30, 169, 174, 86, 8, 6, 221, 145, 122, 68, 60, 125, 2, 17, 0, 0, 0, 3, 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