Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05141f7d42c811cfb5b15702389fcbcecf050f4d96c1899f9478df073c415d7f

Tx prefix hash: bd8bdee4ea16a485c6793f6751c67d257b0ebab1db7eed7440644b525bcc1129
Tx public key: 888cf910f29258f454b9bc71223b4d9c8477560d6beea9c2dbde4bbfd143580c
Timestamp: 1718236544 Timestamp [UCT]: 2024-06-12 23:55:44 Age [y:d:h:m:s]: 00:275:14:59:39
Block: 1042934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196982 RingCT/type: yes/0
Extra: 01888cf910f29258f454b9bc71223b4d9c8477560d6beea9c2dbde4bbfd143580c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 639e528cc8503db0e0e08d78eaa60254213546f3e58f7ca8ad672e00474c483f 0.600000000000 1511965 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": 1042944, "vin": [ { "gen": { "height": 1042934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639e528cc8503db0e0e08d78eaa60254213546f3e58f7ca8ad672e00474c483f" } } ], "extra": [ 1, 136, 140, 249, 16, 242, 146, 88, 244, 84, 185, 188, 113, 34, 59, 77, 156, 132, 119, 86, 13, 107, 238, 169, 194, 219, 222, 75, 191, 209, 67, 88, 12, 2, 17, 0, 0, 0, 3, 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