Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e6f4b1eee42c6b594f6d834007d528c916a7ce236a0382b3a86ab7576da6b6

Tx prefix hash: 25db9300f72904ceb2f3e120863eacd3e4cead6a3ac0da0f2e2d427eabae9f48
Tx public key: 9cb7f487e0d82668ecaaa7084e2faafaa9c7c1719ebbe7307f39127a23db082b
Timestamp: 1740186743 Timestamp [UCT]: 2025-02-22 01:12:23 Age [y:d:h:m:s]: 00:229:11:35:24
Block: 1224438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161731 RingCT/type: yes/0
Extra: 019cb7f487e0d82668ecaaa7084e2faafaa9c7c1719ebbe7307f39127a23db082b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a54c972c04f460552936c724221046ea373045f7f9330ad2913a3092e4f8fb57 0.600000000000 1711301 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": 1224448, "vin": [ { "gen": { "height": 1224438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54c972c04f460552936c724221046ea373045f7f9330ad2913a3092e4f8fb57" } } ], "extra": [ 1, 156, 183, 244, 135, 224, 216, 38, 104, 236, 170, 167, 8, 78, 47, 170, 250, 169, 199, 193, 113, 158, 187, 231, 48, 127, 57, 18, 122, 35, 219, 8, 43, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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