Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c8f66bc14a00ac458ec859bd38abf8f7ff5fb531e6c60999df854206dd6f583

Tx prefix hash: f7158fa008fcefccdc8fb7aff56eef061afcf1ab442046c23e8ff6b0bae23231
Tx public key: f5c1447c7f7e6104fb0cb3b86d885554fdb30d4f1e401a8dd601376e53ceae8a
Timestamp: 1763963171 Timestamp [UCT]: 2025-11-24 05:46:11 Age [y:d:h:m:s]: 00:004:01:08:15
Block: 1418906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2895 RingCT/type: yes/0
Extra: 01f5c1447c7f7e6104fb0cb3b86d885554fdb30d4f1e401a8dd601376e53ceae8a0211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482458852a80ccdd9c651b89d50206b5313a7d82b86902bfa9fa2d59d80a977c 0.600000000000 1907439 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": 1418916, "vin": [ { "gen": { "height": 1418906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482458852a80ccdd9c651b89d50206b5313a7d82b86902bfa9fa2d59d80a977c" } } ], "extra": [ 1, 245, 193, 68, 124, 127, 126, 97, 4, 251, 12, 179, 184, 109, 136, 85, 84, 253, 179, 13, 79, 30, 64, 26, 141, 214, 1, 55, 110, 83, 206, 174, 138, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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