Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3dc2ed07c0957d16a5c7754b12cb705fa4268e1e3da08df8700444d5131e93a

Tx prefix hash: 10878ef5d1c49a8273ba7b1c8ccd1ac6411018391647691ff2a52d7e966c20c9
Tx public key: dd296a2e1d32daa3ffe2e132ff7148d74238ae2ed960621c468d773dee978095
Timestamp: 1724330606 Timestamp [UCT]: 2024-08-22 12:43:26 Age [y:d:h:m:s]: 00:223:03:35:44
Block: 1093472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159336 RingCT/type: yes/0
Extra: 01dd296a2e1d32daa3ffe2e132ff7148d74238ae2ed960621c468d773dee97809502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f4e7600fc6113d3d5f32d7d80611bb7bfc84a624dd321e74df6d0862f4c7a26 0.600000000000 1568423 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": 1093482, "vin": [ { "gen": { "height": 1093472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f4e7600fc6113d3d5f32d7d80611bb7bfc84a624dd321e74df6d0862f4c7a26" } } ], "extra": [ 1, 221, 41, 106, 46, 29, 50, 218, 163, 255, 226, 225, 50, 255, 113, 72, 215, 66, 56, 174, 46, 217, 96, 98, 28, 70, 141, 119, 61, 238, 151, 128, 149, 2, 17, 0, 0, 0, 5, 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