Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11265a3b4ab764eee028ea5faff1b7c11581cc308f45bb91b80b9d2f1d2b649a

Tx prefix hash: e0f1049976a7e8ade17fb8cc6777429265e60989e71b589c88bcd6b225fd308c
Tx public key: db3c71a0f70b00f343ed2fa7b5d211ed61290b8da5d3fd2cedf1359ba8569067
Timestamp: 1757536863 Timestamp [UCT]: 2025-09-10 20:41:03 Age [y:d:h:m:s]: 00:104:01:16:24
Block: 1365652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74488 RingCT/type: yes/0
Extra: 01db3c71a0f70b00f343ed2fa7b5d211ed61290b8da5d3fd2cedf1359ba8569067021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f2d81401755c25db30da9cf8b598c4ada706a1bb316b489c69a90de1089ba84 0.600000000000 1853691 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": 1365662, "vin": [ { "gen": { "height": 1365652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2d81401755c25db30da9cf8b598c4ada706a1bb316b489c69a90de1089ba84" } } ], "extra": [ 1, 219, 60, 113, 160, 247, 11, 0, 243, 67, 237, 47, 167, 181, 210, 17, 237, 97, 41, 11, 141, 165, 211, 253, 44, 237, 241, 53, 155, 168, 86, 144, 103, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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