Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf569d60fde2c465e89d42fc28c7240e5adedb1406d37921c276af7e0f605b5

Tx prefix hash: a924e383384b52ca1e7767151c46c7ff09cde574ec5c87829efa21eb1c70f85c
Tx public key: 8f2117df4b877182a5a058297a876d5d9cda679f8202d56bda49cc848978d96d
Timestamp: 1724138677 Timestamp [UCT]: 2024-08-20 07:24:37 Age [y:d:h:m:s]: 00:155:10:40:59
Block: 1091878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111142 RingCT/type: yes/0
Extra: 018f2117df4b877182a5a058297a876d5d9cda679f8202d56bda49cc848978d96d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e8a79d1f5d20d35c4b2272b29baeb94f6d8a660f73cbcf7d66dcb487734b370 0.600000000000 1566513 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": 1091888, "vin": [ { "gen": { "height": 1091878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e8a79d1f5d20d35c4b2272b29baeb94f6d8a660f73cbcf7d66dcb487734b370" } } ], "extra": [ 1, 143, 33, 23, 223, 75, 135, 113, 130, 165, 160, 88, 41, 122, 135, 109, 93, 156, 218, 103, 159, 130, 2, 213, 107, 218, 73, 204, 132, 137, 120, 217, 109, 2, 17, 0, 0, 0, 2, 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