Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7cd1deaba25acde775513fe8260058e97fd24c360de3bfe02e1750f12e374bb

Tx prefix hash: 539c37d3588bb55fe6df92a092517e51a664f4c197a4d74e7a17fdb5c7972947
Tx public key: a42cdd7916eea445c8154f5ac4d8e9cf402993f0d020122d71a7921eee334589
Timestamp: 1706245425 Timestamp [UCT]: 2024-01-26 05:03:45 Age [y:d:h:m:s]: 01:030:16:29:50
Block: 943490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282996 RingCT/type: yes/0
Extra: 01a42cdd7916eea445c8154f5ac4d8e9cf402993f0d020122d71a7921eee33458902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2085a78a5a54f9d4bc6a3009e2dc8cf2e5be5c05a4b89dc6d70674aead176d 0.600000000000 1401696 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": 943500, "vin": [ { "gen": { "height": 943490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2085a78a5a54f9d4bc6a3009e2dc8cf2e5be5c05a4b89dc6d70674aead176d" } } ], "extra": [ 1, 164, 44, 221, 121, 22, 238, 164, 69, 200, 21, 79, 90, 196, 216, 233, 207, 64, 41, 147, 240, 208, 32, 18, 45, 113, 167, 146, 30, 238, 51, 69, 137, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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