Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52e99045b746d68e72e49d0bd55b868bbb402db47ad39afb0ee90f51e6fc232

Tx prefix hash: dfe07930522b484aa689beb73233195efab2e43a7a2bcddceed06adc43b84d0a
Tx public key: f3a23783bc42b02e6f4a7a532f53a55dc3f5b870ab2e68b5e62a0c1652bb6fa2
Timestamp: 1745056203 Timestamp [UCT]: 2025-04-19 09:50:03 Age [y:d:h:m:s]: 00:216:07:29:43
Block: 1264774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152316 RingCT/type: yes/0
Extra: 01f3a23783bc42b02e6f4a7a532f53a55dc3f5b870ab2e68b5e62a0c1652bb6fa202110000000bdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91313b474b8716af0dbd5c26d63fcee33b35bf2a30dd88e86143b4c90a950642 0.600000000000 1751975 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": 1264784, "vin": [ { "gen": { "height": 1264774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91313b474b8716af0dbd5c26d63fcee33b35bf2a30dd88e86143b4c90a950642" } } ], "extra": [ 1, 243, 162, 55, 131, 188, 66, 176, 46, 111, 74, 122, 83, 47, 83, 165, 93, 195, 245, 184, 112, 171, 46, 104, 181, 230, 42, 12, 22, 82, 187, 111, 162, 2, 17, 0, 0, 0, 11, 219, 181, 113, 193, 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