Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe0447107c6169dd21aa2c1b7e3373243054bb4deb55ad286132745120eb655a

Tx prefix hash: d8b072d03d1b10e04306a4fd0e5f365e412cb6d9c80c22076dfc334d27bf5f47
Tx public key: 593196d235620948bf97baa9b5879d0acb588d263671f9917bd1abaf0df28ad2
Timestamp: 1713261741 Timestamp [UCT]: 2024-04-16 10:02:21 Age [y:d:h:m:s]: 00:317:10:34:33
Block: 1001678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226924 RingCT/type: yes/0
Extra: 01593196d235620948bf97baa9b5879d0acb588d263671f9917bd1abaf0df28ad20211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7c7f70a4a7c4442c14e9893ad8176684dbf9275bf58fa7463b6c6a7d4b692d 0.600000000000 1462186 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": 1001688, "vin": [ { "gen": { "height": 1001678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7c7f70a4a7c4442c14e9893ad8176684dbf9275bf58fa7463b6c6a7d4b692d" } } ], "extra": [ 1, 89, 49, 150, 210, 53, 98, 9, 72, 191, 151, 186, 169, 181, 135, 157, 10, 203, 88, 141, 38, 54, 113, 249, 145, 123, 209, 171, 175, 13, 242, 138, 210, 2, 17, 0, 0, 0, 4, 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