Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 882453f977de43950938022bf1bc1abcbdef6d7153165cf4d9f069929ad19115

Tx prefix hash: 8b7418cf682dc263adda964a9c9cf6af895c5b1a3abc5db95ed8a9ee05a8d32f
Tx public key: 01729a0ca14fd677f9d0e537fb3191a567698281f567e28b036f32a47141879d
Timestamp: 1694231843 Timestamp [UCT]: 2023-09-09 03:57:23 Age [y:d:h:m:s]: 02:069:08:28:42
Block: 844105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569267 RingCT/type: yes/0
Extra: 0101729a0ca14fd677f9d0e537fb3191a567698281f567e28b036f32a47141879d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.979782765000 dcy

stealth address amount amount idx
00: 0c5de37ec5b2b00650bb10d7b9e085e616e5b832713ef3d69190094f8471255a 0.979782765000 1297391 of 0

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": 844115, "vin": [ { "gen": { "height": 844105 } } ], "vout": [ { "amount": 979782765, "target": { "key": "0c5de37ec5b2b00650bb10d7b9e085e616e5b832713ef3d69190094f8471255a" } } ], "extra": [ 1, 1, 114, 154, 12, 161, 79, 214, 119, 249, 208, 229, 55, 251, 49, 145, 165, 103, 105, 130, 129, 245, 103, 226, 139, 3, 111, 50, 164, 113, 65, 135, 157, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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