Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be37798078c71e7f9907f40fd73b34c2339b7ec1cc69b9ea4de4e98c5ddfc8d8

Tx prefix hash: b36dee5daa07ec6354170ec4af29e3e6c8d35c247f22bed9190a3ca30c5f0a60
Tx public key: 670139fccb19a9d914aca7e035f9857845a886c682a5e4cfe873a0671e93e02d
Timestamp: 1725344388 Timestamp [UCT]: 2024-09-03 06:19:48 Age [y:d:h:m:s]: 00:173:01:53:27
Block: 1101865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123500 RingCT/type: yes/0
Extra: 01670139fccb19a9d914aca7e035f9857845a886c682a5e4cfe873a0671e93e02d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bc3dacc5e6938e782f45df74dab6775b16348ce40b4107ada37fcdac93c11c0 0.600000000000 1578078 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": 1101875, "vin": [ { "gen": { "height": 1101865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bc3dacc5e6938e782f45df74dab6775b16348ce40b4107ada37fcdac93c11c0" } } ], "extra": [ 1, 103, 1, 57, 252, 203, 25, 169, 217, 20, 172, 167, 224, 53, 249, 133, 120, 69, 168, 134, 198, 130, 165, 228, 207, 232, 115, 160, 103, 30, 147, 224, 45, 2, 17, 0, 0, 0, 7, 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