Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0694b9a543b99ff14f781b7f2709deab8e8ab393309dd12ff5a65d7fbbf745a3

Tx prefix hash: 57d2d69bf4b0f76e7157b30d5605e012cfd2c38f8d20319aa8a94273037ab14a
Tx public key: d2196dc59221f74b4efec9dee82ce5090b848d6a9755858f481485057c53aea9
Timestamp: 1740282365 Timestamp [UCT]: 2025-02-23 03:46:05 Age [y:d:h:m:s]: 00:343:08:29:33
Block: 1225237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243077 RingCT/type: yes/0
Extra: 01d2196dc59221f74b4efec9dee82ce5090b848d6a9755858f481485057c53aea9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aaf2a35c110aaf3c3748a6e4165ed9c3f6b9196f418939fa61b505c33c25f92 0.600000000000 1712102 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": 1225247, "vin": [ { "gen": { "height": 1225237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aaf2a35c110aaf3c3748a6e4165ed9c3f6b9196f418939fa61b505c33c25f92" } } ], "extra": [ 1, 210, 25, 109, 197, 146, 33, 247, 75, 78, 254, 201, 222, 232, 44, 229, 9, 11, 132, 141, 106, 151, 85, 133, 143, 72, 20, 133, 5, 124, 83, 174, 169, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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