Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e79f45f4d7476a6c96e1455de9213056e3e6b218531f7a9e1fae4649e3f9c929

Tx prefix hash: f0139238614a46d6ef15b0a40e6999f606a4e35fd522561fd23ef9d2f8609f51
Tx public key: c3c23968f09ae83f52f078100a7b839d59e437891a5af33743a53eff0a697564
Timestamp: 1720189405 Timestamp [UCT]: 2024-07-05 14:23:25 Age [y:d:h:m:s]: 00:231:23:14:34
Block: 1059121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165694 RingCT/type: yes/0
Extra: 01c3c23968f09ae83f52f078100a7b839d59e437891a5af33743a53eff0a6975640211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9ac8acb7c955f46cf0f098718e9d8e7ff3ac0febc22540eb002cf1914f565dc 0.600000000000 1529582 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": 1059131, "vin": [ { "gen": { "height": 1059121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9ac8acb7c955f46cf0f098718e9d8e7ff3ac0febc22540eb002cf1914f565dc" } } ], "extra": [ 1, 195, 194, 57, 104, 240, 154, 232, 63, 82, 240, 120, 16, 10, 123, 131, 157, 89, 228, 55, 137, 26, 90, 243, 55, 67, 165, 62, 255, 10, 105, 117, 100, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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