Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc5a28319e10774e2724098642037fd2fb859e1406d5cc059f345f93f93aa685

Tx prefix hash: 12dc5ace3a0314e4c15a3793cc16f2b5d3cdc0b4675e7922aaaef3d56087b143
Tx public key: 334cf01c3d15e87adf5cb839febaa2cb923d1c55a687267cfa78bebe00908861
Timestamp: 1732087080 Timestamp [UCT]: 2024-11-20 07:18:00 Age [y:d:h:m:s]: 00:358:16:27:07
Block: 1157663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253909 RingCT/type: yes/0
Extra: 01334cf01c3d15e87adf5cb839febaa2cb923d1c55a687267cfa78bebe009088610211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed5f02df5b88cd4e93f51dadfe56bc3a2e76b0b385c5583ae947a415625d3067 0.600000000000 1643286 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": 1157673, "vin": [ { "gen": { "height": 1157663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed5f02df5b88cd4e93f51dadfe56bc3a2e76b0b385c5583ae947a415625d3067" } } ], "extra": [ 1, 51, 76, 240, 28, 61, 21, 232, 122, 223, 92, 184, 57, 254, 186, 162, 203, 146, 61, 28, 85, 166, 135, 38, 124, 250, 120, 190, 190, 0, 144, 136, 97, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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