Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6ee55d29f513ef5949c52d4c07ee246ba63a35359a68db7c6e9bcfc85fb72d

Tx prefix hash: 35845a99c1117587b4407ada1cb6f95c8ff37d20130c4d766905e8ef7c31fee2
Tx public key: 750c52ff1bb3ed869fb7f9462e26245ab758e58d511b0de42e7ee0ac9a7b50df
Timestamp: 1713130208 Timestamp [UCT]: 2024-04-14 21:30:08 Age [y:d:h:m:s]: 00:212:10:51:35
Block: 1000577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152101 RingCT/type: yes/0
Extra: 01750c52ff1bb3ed869fb7f9462e26245ab758e58d511b0de42e7ee0ac9a7b50df02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48d56eb6562101cb4b7617124a8d2a741e59d2afdbbff12fe1dd1825015186ac 0.600000000000 1461075 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": 1000587, "vin": [ { "gen": { "height": 1000577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48d56eb6562101cb4b7617124a8d2a741e59d2afdbbff12fe1dd1825015186ac" } } ], "extra": [ 1, 117, 12, 82, 255, 27, 179, 237, 134, 159, 183, 249, 70, 46, 38, 36, 90, 183, 88, 229, 141, 81, 27, 13, 228, 46, 126, 224, 172, 154, 123, 80, 223, 2, 17, 0, 0, 0, 5, 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