Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476500c2a85f1910f3e283ba6e8025ba0caf06fb56c1394176df2b25227f207e

Tx prefix hash: 43c635a853717d188e091b3b5dd882351fe51eb166f4c3ec1474d15a679347d2
Tx public key: 9fa304d0d31a1986d9f0d9d8d08e6c7a63378a02079c3065f1918f192c152e70
Timestamp: 1731201765 Timestamp [UCT]: 2024-11-10 01:22:45 Age [y:d:h:m:s]: 00:014:14:11:51
Block: 1150345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10444 RingCT/type: yes/0
Extra: 019fa304d0d31a1986d9f0d9d8d08e6c7a63378a02079c3065f1918f192c152e70021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9114ad59126fbfc46093f26e7ca2d3ac5c0291fc067cb5a4d4eb8a471c63bb3f 0.600000000000 1635630 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": 1150355, "vin": [ { "gen": { "height": 1150345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9114ad59126fbfc46093f26e7ca2d3ac5c0291fc067cb5a4d4eb8a471c63bb3f" } } ], "extra": [ 1, 159, 163, 4, 208, 211, 26, 25, 134, 217, 240, 217, 216, 208, 142, 108, 122, 99, 55, 138, 2, 7, 156, 48, 101, 241, 145, 143, 25, 44, 21, 46, 112, 2, 17, 0, 0, 0, 2, 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