Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17b37b5c29313747a6784ba8af7e745a4b7b1aa876551ff099969dde29091c92

Tx prefix hash: 42d9833d62e79cf4ba2e3f6df574bc128f162db7a538f0cab86003a9cdad1ad0
Tx public key: de1144b2e324a5891bd57821bd1c37b83a92a505b3898f26f58189f8a470a00e
Timestamp: 1749492497 Timestamp [UCT]: 2025-06-09 18:08:17 Age [y:d:h:m:s]: 00:163:14:10:46
Block: 1301516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114597 RingCT/type: yes/0
Extra: 01de1144b2e324a5891bd57821bd1c37b83a92a505b3898f26f58189f8a470a00e021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 259de1b5312ab42262d8aca564b905e583f63e0d10b48af2ebdccdbf88e0fdbd 0.600000000000 1789075 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": 1301526, "vin": [ { "gen": { "height": 1301516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "259de1b5312ab42262d8aca564b905e583f63e0d10b48af2ebdccdbf88e0fdbd" } } ], "extra": [ 1, 222, 17, 68, 178, 227, 36, 165, 137, 27, 213, 120, 33, 189, 28, 55, 184, 58, 146, 165, 5, 179, 137, 143, 38, 245, 129, 137, 248, 164, 112, 160, 14, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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