Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fdd126cd79c3aa37cac13d32a4f8d401bcc6f636b3ce3890621b772da8ad9af

Tx prefix hash: 074ad64f917a8b82a5035aa078242a359a6bbe3d0fb332af72e9b85ed8329413
Tx public key: 9975ca1fe810b947496a8f8cff9733a835e9db19ad11c247d6f1f43a4cee336e
Timestamp: 1735977818 Timestamp [UCT]: 2025-01-04 08:03:38 Age [y:d:h:m:s]: 00:102:03:09:11
Block: 1189896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72775 RingCT/type: yes/0
Extra: 019975ca1fe810b947496a8f8cff9733a835e9db19ad11c247d6f1f43a4cee336e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fef5d7d47c672321f8ddc92fde104cf5b83aab7bb47b209ed884d9cb58e3418d 0.600000000000 1676411 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": 1189906, "vin": [ { "gen": { "height": 1189896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fef5d7d47c672321f8ddc92fde104cf5b83aab7bb47b209ed884d9cb58e3418d" } } ], "extra": [ 1, 153, 117, 202, 31, 232, 16, 185, 71, 73, 106, 143, 140, 255, 151, 51, 168, 53, 233, 219, 25, 173, 17, 194, 71, 214, 241, 244, 58, 76, 238, 51, 110, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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