Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140b8078fe62a8951c4919ad3760f2534b05d197653e597ad08a598890bd6150

Tx prefix hash: e75ea8f0998fe226c0e2f1f4f84b0a4e82620a91083c3f0f5617fb1a09db3ad8
Tx public key: 32faaf460040e40c0a7e7eb78eda928f0d1bf58b20bc7f803abf798ebf168d56
Timestamp: 1715896809 Timestamp [UCT]: 2024-05-16 22:00:09 Age [y:d:h:m:s]: 00:329:05:44:00
Block: 1023541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235331 RingCT/type: yes/0
Extra: 0132faaf460040e40c0a7e7eb78eda928f0d1bf58b20bc7f803abf798ebf168d5602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6b3f6abd85249388460b8e5e66c7e1c976551802b2fb6bcea50a24ad954afc 0.600000000000 1488588 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": 1023551, "vin": [ { "gen": { "height": 1023541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6b3f6abd85249388460b8e5e66c7e1c976551802b2fb6bcea50a24ad954afc" } } ], "extra": [ 1, 50, 250, 175, 70, 0, 64, 228, 12, 10, 126, 126, 183, 142, 218, 146, 143, 13, 27, 245, 139, 32, 188, 127, 128, 58, 191, 121, 142, 191, 22, 141, 86, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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