Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e77c394b573ebdd512bd0ce45a579dc926c1391ab526322cbbb2a27d813e2441

Tx prefix hash: 09a37c88e7c7d85f4609ecb746d8b2797d7dc55f670ad568bd2ccc71ac30a5f5
Tx public key: 2696ee0f5d73102daabeaa9b68e3752875ea7bb4e99fb3fd9643122894dbcb76
Timestamp: 1733140698 Timestamp [UCT]: 2024-12-02 11:58:18 Age [y:d:h:m:s]: 00:195:09:48:21
Block: 1166398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139408 RingCT/type: yes/0
Extra: 012696ee0f5d73102daabeaa9b68e3752875ea7bb4e99fb3fd9643122894dbcb76021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13d6905e340f6cbaf416135a5d2210a7ee7c78177d81336536eaa52c2b01e16d 0.600000000000 1652085 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": 1166408, "vin": [ { "gen": { "height": 1166398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13d6905e340f6cbaf416135a5d2210a7ee7c78177d81336536eaa52c2b01e16d" } } ], "extra": [ 1, 38, 150, 238, 15, 93, 115, 16, 45, 170, 190, 170, 155, 104, 227, 117, 40, 117, 234, 123, 180, 233, 159, 179, 253, 150, 67, 18, 40, 148, 219, 203, 118, 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